MacHack 1995/MacHack 1995.toast/Presentations/Presentations ’90/John Norstad/Disinfectant 2.0b2/Disinfectant 2.0b2.rsrc/STR#_218.txt

Text File | 1990-06-12 | 11KB | 567 lines



servers, see the “Special Features” section.

Disinfectant from the virus tools floppy. For more details on scanning

start up the server Mac using your virus tools floppy disk, and run

errors, we recommend that you remove the server from production,

which you do not have the necessary access privileges. To avoid these

These error messages are issued if a server folder is encountered for



### cannot be checked.

### privileges to this folder. This folder

### You have neither See Files nor See Folders



### cannot be checked.

### to this folder. Folders within this folder

### You do not have See Folders privilege



### cannot be checked.

### to this folder. Files within this folder

### You do not have See Files privilege



### WARNING: This file is still infected!

### It cannot be repaired.

### to the folder containing this file.

### You do not have Make Changes privilege



### files in those folders may be infected!

### to access files in some of the folders. Some

### WARNING: You do not have the proper privileges







(“File” and “Res” privileges for “Other,” “System” and “Self”).

Disinfectant privileges. You should grant Disinfectant all privileges

files on a GateKeeper-protected system when you have forgotten to grant

One possible cause of unexpected errors is attempting to repair infected



### WARNING: This file is probably still infected!

### granted privileges to Disinfectant.

### GateKeeper, check to make certain you have

### Unexpected error (nnn). If you are using







us a copy of the file that was being scanned when the error occurred.

specify the error number reported in the message. If possible, also send

author describing what you were doing when the error occurred. Please

in Disinfectant. We would appreciate it if you would send a note to the

Unexpected errors should not occur. It means that there may be an error



### WARNING: This file is still infected!

### to open this file for repair.

### Unexpected error (nnn) occurred while trying



### Unexpected error (nnn).









release disks.

damaged System file and replace it with a copy from original locked Apple

file is damaged and should not be used. You should immediately delete the

Disinfectant issues a special error message, telling you that the resulting

resources, but it does not replace the Apple versions. In this situation,

resources. When Disinfectant repairs the file, it deletes the Scores viral

Apple’s versions of these resources with the Scores viral versions of the

those used by Scores. When Scores infects the System file, it replaces

6.0.4, Apple began using some resources with the same type and id as

Apple’s System Software release 6.0.4 and later releases. In System

release 6.0.4 or later. There is a serious conflict between Scores and

Scores virus has infected a System file from Apple’s System Software

This error message is currently issued in only one situation: when the



You should delete it and replace it with a known good copy of the file.

file, but leaves the file damaged. You should not attempt to use such a file.

repaired properly. In this case, Disinfectant removes the virus from the

Viruses sometimes damage files in such a way that they cannot be



### and replace it with a known good copy.

### be repaired properly. You should delete the file

### This file was damaged by the virus, and it cannot







the “Special Features” section.

should avoid file busy errors. For more details on scanning servers, see

tools floppy disk, and run Disinfectant from the virus tools floppy. This

the server from production, start up the server Mac using your virus

Finder or MultiFinder). For server disks, we recommend that you remove

This error is also possible when scanning server disks (under either

running Disinfectant under MultiFinder. Try again without MultiFinder.

by some other application. The most common cause of this error is

Your file could not be opened for writing because the file was already open



### WARNING: This file is still infected!

### Try using Finder instead of MultiFinder.

### This file is busy and cannot be repaired.







see the “Special Features” section.

This should avoid file busy errors. For more details on scanning servers,

virus tools floppy disk, and run Disinfectant from the virus tools floppy.

remove the server from production, start up the server Mac using your

only occur on server disks. For server disks, we recommend that you

with exclusive access by some other application. This message should

Your file could not be opened for reading because the file was already open



### This file is busy and cannot be checked.







Another possible cause of this error is that the file is damaged.



this error message.

them for viruses and if there is not enough memory available you will get

resources. Disinfectant must load these resources into memory to check

This error can be caused by applications which contain very large



without MultiFinder.

This message is quite rare. You might try running Disinfectant again

Disinfectant was unable to get enough memory to check or repair the file.



### WARNING: This file is probably still infected!

### There is not enough memory to repair this file.



### There is not enough memory to check this file.







Reflex.

These files are not really damaged—they are still usable, but only by

Reflex makes non-standard use of the resource fork in its database files.

Disinfectant also reports that all Reflex database files are “damaged.”



stores the archived files in the data fork, not the resource fork.

archive files. These “damaged” files are usually still usable since StuffIt

For some reason, we have seen this problem with a number of StuffIt



with the file and you should replace it with a known good copy of the file.

and system files, this usually indicates that something is seriously wrong

usable. For document files, this is usually not a problem. For applications

is not valid resource information. The data fork may still be intact and

fork. This message means that the information stored in the resource fork

data fork. When Disinfectant checks a file, it tries to open the resource

Macintosh files have two parts or “forks”—the resource fork and the



### in an unknown format. It cannot be checked.

### The resource fork of this file is damaged or







Disinfectant again.

the files on the disk to some other disk to make more room and run

free space on the disk before it can repair the file. Try moving some of

infected file on the disk. Disinfectant requires at least a small amount of

This error may occur if a disk is very full and you attempt to repair an



### WARNING: This file may still be infected!

### The disk is too full to repair this file.







send a report to the author.

probably an error in Disinfectant. We would appreciate it if you would

If this error occurs in some other situation, it means that there is



which the disk is directly connected.

over the network. We recommend that you scan the disk using the Mac to

network. TOPS does not permit access to currently active System files

This error should only occur if you try to scan a disk over a TOPS



### System files cannot be scanned over TOPS.







You canceled a scan or disinfection run.



### Scan canceled.







error messages occurred during a scan.

This message appears in the summary section of the report if any other



### and click on the error message text.

### explanation of an error message, press Command-?

### NOTE: Some errors were reported. For a detailed







message. We have never encountered this situation in actual practice.

knowing which virus originally attacked the file, so it issues this special

present in an infected file. In this case, Disinfectant has no way of

identical. It is theoretically possible for only these common parts to be

nVIR A and nVIR B are different viruses, but some of their parts are



### but not contagious.

### File partially infected by nVIR A or nVIR B,







protection mechanisms.

harmless part of the Scores infection will manage to evade GateKeeper’s

particular, if the Scores virus attacks a GateKeeper-protected system, a

Partial infections can also arise on GateKeeper-protected systems. In



but not all of the infection.

which have errors. The other virus tool may remove part of an infection,

Partially infected files sometimes are the result of other virus tools



the file or you may use Disinfectant to remove the infection.

they cannot spread to other files. You may chose to leave the infection on

infection is not contagious. These kinds of infections are not dangerous and

Your file is partially infected by the virus named “xxxxx,” but the



### but not contagious.

### File partially infected by xxxxx,







WDEF virus for more information.

if you would send us a copy of the infected file. See the section on the

reported. If you have not already repaired the file, we would appreciate it

Your file is infected by a strain of the WDEF virus which has not yet been



### File infected by an unknown strain of WDEF







(Scores, nVIR A, etc.).

Your file is infected by a virus. “xxxxx” is the name of the virus



### File infected by xxxxx.







intermittent, it might work the second time.

Disinfectant again on the same file. If the hardware problem is

or the disk drive is not operating properly. You can try running

while trying to read or write a file. They usually mean that the disk itself

These error messages are listed in the report if a hardware error occurs



### WARNING: This file may still be infected!

### this file.

### An I/O error occurred while trying to repair



### this file.

### An I/O error occurred while trying to check







properly.

application damaged in such a way that Disinfectant cannot repair it

handle multiple infections properly and they sometimes leave the

repair the file before running Disinfectant. Some other virus tools cannot

by more than one virus and you attempt to use some other virus tool to

One situation in which this error can occur is if an application is infected



not common, but it can occur in unusual situations.

or it may be damaged in such a way that it cannot be used. This error is

longer infected, you can try running it to see if it works. It may be usable

is still infected, you should delete it. If Disinfectant reports that it is no

Scan the file again with Disinfectant to find out if it is still infected. If it

discovered something wrong with the file. The file may still be infected.

Your file was infected, but while attempting to repair it Disinfectant



### WARNING: This file may still be infected!

### trying to repair this file.

### An error or inconsistency was detected while





order, with a brief explanation of each one.

This section presents all of Disinfectant’s error messages, in alphabetical








åError Messages



3




3



ˇˇ